Drug monitoring tool

ABSTRACT

Embodiments of the present disclosure relate to a drug monitoring tool. The drug monitoring tool comprises a data receiver and an interactive user interface. The data receiver is configured to receive a pharmacokinetic (PK) profile of a patient. The interactive user interface is configured to display, to the patient, a time-varying therapeutic plasma protein level of the patient. The time-varying therapeutic plasma protein level is based on an administered dose of a clotting factor VIII and the PK profile of the patient.

RELATED APPLICATIONS

This application claims the benefit of and priority to U.S. provisional patent application Ser. No. 62/451,391, filed Jan. 27, 2017, the content of which is incorporated by reference herein in its entirety.

BACKGROUND

Clotting factor VIII is a blood-clotting protein that is activated in response to an injury or bleed. Individuals with relatively low levels of clotting factor VIII are susceptible to internal or external episodes of prolonged bleeding resulting from an injury and/or spontaneous bleeding without a cause. While skin bleeds are not serious, internal bleeding of joints, muscles, and organs can cause permanent damage, disfigurement, or even death.

Patients with hemophilia A have a genetic deficiency that causes low levels of clotting factor VIII. The amount of clotting factor VIII in a patient is expressed as a percentage relative to a normal level. Patients with 5 to 40% of clotting factor VIII are considered to have a mild form of hemophilia A while patients with 1 to 5% of clotting factor VIII are considered to have a moderate form of hemophilia A. Patients with less than 1% of clotting factor VIII are considered to have a severe form of hemophilia A.

Treatment of patients with hemophilia A (or patients that otherwise have low levels of clotting factor VIII) includes providing these patients with periodic infusions of a clotting factor concentrate (e.g., therapeutic plasma protein). The clotting factor concentrate acts as a replacement or supplement for the patient's natural occurring clotting factor VIII. One example of such a therapeutic plasma protein is Shire's ADVATE drug. In some instances, patients receive the therapeutic plasma protein in response to having an uncontrolled internal bleed. Alternatively, patients may be prescribed a prophylactic treatment regimen of the therapeutic plasma protein to reduce the possibility of future bleeds. To avoid any chance of a patient falling below a predetermined threshold, many healthcare providers design treatment regimens that require patients to receive a therapeutic plasma protein infusion every one, two, three, or more days. Currently, patients are provided with electronic diaries to record infusion events. Unfortunately, such diaries do not provide actionable data from which a patient is able to plan activity levels. For example, with current systems, patients are unable to ascertain a risk of bleeding if the patient were to participate in an activity such as playing soccer at any point in time after an infusion event. In particular, with current electronic diaries, patients cannot determine their factor level at any given point in time after a prophylactic infusion event, significantly limiting the usefulness of the information provided by such sources.

SUMMARY

Embodiments of the present disclosure provide a drug monitoring tool that enables a patient to view a personalized, real-time indication of clotting factor VIII levels following a prophylactic infusion event. Advantageously, the disclosed drug monitoring tool allows a patient to significantly reduce bleeding events. For instance, the real-time indication of clotting factor VIII provided by the drug monitoring tool enables the patient to make informed decisions related to an amount and/or intensity of physical activity at any given point in time. In an example in which the drug monitoring tool provides an indication of a low level of clotting factor VIII, the patient may refrain from participating in a physically demanding activity such as a sport, decide to self-administer a non-prophylactic dose of clotting factor VIII in order to participate in the physically demanding activity, or choose a low bleed risk activity (e.g., a stationary activity such as reading a book) until the next prophylactic infusion. Thus, the drug monitoring tool advantageously eliminates patient bleed events due to a lack of actionable information.

In one embodiment, a drug monitoring tool comprises a data receiver configured to receive a pharmacokinetic (PK) profile of a patient. The tool also comprises an interactive user interface configured to present to a patient a time-varying drug concentration level in the patient. The time-varying drug concentration level is based on an administered dose of a subject drug and the PK profile of the patient.

In another embodiment, disclosed is a drug monitoring tool. The tool comprises a data receiver configured to receive a pharmacokinetic (PK) profile of a patient. In addition, the tool comprises an interactive user interface configured to display to the patient a time-varying therapeutic plasma protein level of the patient. The time-varying therapeutic plasma protein level is based on an administered dose of a clotting factor VIII and the PK profile of the patient.

In one aspect of an embodiment, the PK profile of the patient can be based on a Bayesian model of PK profiles of sampled patients and based upon at least one of a bodyweight, von Willebrand factor (“vWF”) level, and/or an age of the patient.

In another aspect, the data receiver can be a camera configured to scan a quick response (QR) code storing patient information that includes at least PK profile information. Additionally, the drug monitoring tool can further comprise a QR code processor configured to extract and process the patient information stored within the QR code.

In some aspects, the data receiver can be a communications interface configured to receive the PK profile from a secured server. In this aspect, the received PK profile can be encrypted and the communications interface can be further configured to decrypt the encrypted PK profile.

The drug monitoring tool, in other example embodiments, can further comprise a QR code generator configured to generate the QR code having patient information encrypted using AES-256 encryption with cipher block chaining (CBC) and public-key cryptography standards (PKCS) padding. The QR code generator can be located at a secured server remote from the drug monitoring tool.

The QR code can include at least one of or any combination of: patient identifying information, patient physiological data, patient dosing information, and/or PK profile information of the patient. The patient dosing information can include a prophylactic dosing regimen for a particular clotting factor VIII drug

In another aspect, the drug monitoring tool can further comprise an activation toolkit configured to enable access to functionalities of the drug monitoring tool in response to at least one of: receiving the PK profile the patient and/or receiving a log of a first prophylactic infusion of the clotting factor VIII.

In other aspects, the interactive user interface can be configured to display a graphical representation of a time-varying amount of the therapeutic plasma protein within the patient at any given time. The graphical representation can delineate zones associated with the time varying amount of the therapeutic plasma protein. Each zone can be associated with a particular concentration range of the time-varying amount of the therapeutic plasma protein within the patient.

The interactive user interface can also include a graphical control element configured to receive patient input corresponding to a request for the time-varying amount of the therapeutic plasma protein within the patient at a particular time. The interactive user interface can be further configured to display the graphical representation of the time varying amount of the therapeutic plasma protein within the patient at the particular time.

A further embodiment includes a method for drug monitoring executed by a drug monitoring tool. The method includes receiving a pharmacokinetic (PK) profile of a patient. In addition, the method includes enabling an interactive user interface to display to a patient a time-varying therapeutic plasma protein level of the patient. The time-varying therapeutic plasma protein level is based on an administered dose of a clotting factor VIII and the PK profile of the patient.

In one aspect of an embodiment, the PK profile of the patient can be based on a Bayesian model of PK profiles of sampled patients and based upon at least one of a bodyweight, von Willebrand factor (“vWF”) level, and/or an age of the patient.

In another aspect, the method can include scanning a quick response (QR) code storing patient information that includes at least PK profile information. In addition, the method can include extracting and processing the patient information stored within the QR code.

In other aspects, the method can include receiving the PK profile from a secured server. The received PK profile can be encrypted. Accordingly, the method can also include decrypting the encrypted PK profile.

In additional aspects, the method can include generating the QR code to have patient information encrypted using AES-256 encryption with cipher block chaining (CBC) and public-key cryptography standards (PKCS) padding.

In certain aspects, the QR code includes at least one of or any combination of: patient identifying information, patient physiological data, patient dosing information, and/or PK profile information of the patient. The patient dosing information can include a prophylactic dosing regimen for a particular clotting factor VIII drug.

Also, the method can include enabling patient access to functionalities of the drug monitoring tool in response to at least of: receiving the PK profile the patient and/or receiving a log of a first prophylactic infusion.

In further aspects, the method can include displaying a graphical representation of a time-varying amount of the therapeutic plasma protein within the patient at any given time. The graphical representation delineates zones associated with the time varying amount of the therapeutic plasma protein. Each zone is associated with a particular concentration range of the time-varying amount of the therapeutic plasma protein within the patient.

Another embodiment of the present disclosure includes a drug monitoring system. The drug monitoring system comprises a therapeutic plasma protein dosing regimen apparatus and a drug monitoring tool.

The therapeutic plasma protein dosing regimen apparatus comprises a model generator configured to create a Bayesian model of pharmacokinetic (PK) profiles of sampled patients. The Bayesian model includes (i) a therapeutic plasma protein clearance and (ii) a volume of distribution relationship for a therapeutic plasma protein based upon at least one of patient age or body weight. The therapeutic plasma protein dosing regimen apparatus also comprises a PK server. The PK server is configured to determine an approximate PK profile of a patient based upon the Bayesian model, a half-life of the therapeutic plasma protein within the patient, and at least one of an age of the patient or a weight of the patient. The PK server is also configured to determine the therapeutic plasma protein dosing regimen including a dosage and a therapeutic plasma protein level over a time period based upon the approximate PK profile of the patient, modify the therapeutic plasma protein dosing regimen in response to receiving a dosing interval for applying a dosage to the patient, and transmit the modified therapeutic plasma protein dosing regimen to the client device.

The drug monitoring tool comprises a data receiver configured to receive the pharmacokinetic (PK) profile of a patient. In addition, the drug monitoring tool comprises an interactive user interface configured to display to the patient a time-varying therapeutic plasma protein level of the patient. The time-varying therapeutic plasma protein level is based on an administered dose of a clotting factor VIII and the PK profile of the patient.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing will be apparent from the following more particular description of example embodiments of the disclosure, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating embodiments of the present disclosure.

FIG. 1 illustrates an example pharmacokinetic (PK) environment in which a drug monitoring tool operates, according to an example embodiment of the present disclosure.

FIG. 2 is a flow diagram of a method for generating a PK profile of a particular patient in accordance with an example embodiment of the present disclosure.

FIG. 3 is a flow diagram of a method for converting a PK profile into a QR code in accordance with an example embodiment of the present disclosure.

FIG. 4 illustrates an interactive user interface of a drug monitoring tool in accordance with an example embodiment of the present disclosure.

FIG. 5 is a detailed block diagram of an example remote server, drug monitoring tool, and ecosystem monitoring system in accordance with an example embodiment of the present disclosure.

DETAILED DESCRIPTION

A description of example embodiments of the present disclosure follows.

The present disclosure relates a drug monitoring tool that enables a patient to view a personalized, real-time indication of clotting factor VIII levels following a prophylactic infusion event. For example, the drug monitoring tool includes a factor meter that enables a user to determine a real-time level of clotting factor VIII. Armed with such information, patients would be better equipped, for example, to determine whether or not they should participate in a physically demanding activity (e.g., a sport such as soccer). Accordingly, the drug monitoring tool enables patients to make informed decisions with respect to their activity levels based on accurate information of their clotting factor VIII levels. In addition, the factor meter provided by the drug monitoring tool enables patients to determine a time-varying amount of clotting factor VIII in their system at any given time after a prophylactic infusion event. Advantageously, patients are then able to plan activity levels in the future based on predicted clotting factor VIII levels.

As used herein, the term “clotting factor VIII”, “FVIII”, or “rAHF” refers to any FVIII molecule that has at least a portion of the B domain intact, and which exhibits biological activity that is associated with native FVIII. In one embodiment of the disclosure, the FVIII molecule is full-length FVIII. The FVIII molecule is a protein that is encoded by DNA sequences capable of hybridizing to DNA encoding FVIII:C. Such a protein may contain amino acid deletions at various sites between or within the domains A1-A2-B-A3-C1-C2. The FVIII molecule may also be an analog of native clotting factor FVIII, wherein one or more amino acid residues have been replaced by site-directed mutagenesis.

The term “recombinant Factor VIII” (rFVIII) may include any rFVIII, heterologous or naturally occurring, obtained via recombinant DNA technology, or a biologically active derivative thereof. As used herein, “endogenous FVIII” includes FVIII which originates from a mammal intended to receive treatment. The term also includes FVIII transcribed from a transgene or any other foreign DNA present in the mammal. As used herein, “exogenous FVIII” or therapeutic plasma protein includes clotting factor FVIII that does not originate from a mammal.

The FVIII molecule exists naturally and in therapeutic preparations as a heterogeneous distribution of polypeptides arising from a single gene product. The term “clotting factor VIII” as used herein refers to all such polypeptides, whether derived from blood plasma or produced through the use of recombinant DNA techniques and includes, but is not limited to FVIII mimetics, fc-FVIII conjugates, FVIII chemically modified with water soluble polymers, and other forms or derivatives of FVIII. Commercially available examples of therapeutic preparations containing FVIII include those sold under the trade names of ADVATE, HEMOFIL M, and RECOMBINATE (available from Shire, Bannockburn, Ill., U.S.A.). Other preparations comprise primarily a single subpopulation of FVIII molecules, which lack the B domain portion of the molecule.

The FVIII molecules useful for the present disclosure include a full-length protein, precursors of the protein, biologically active or functional subunits or fragments of the protein, and/or functional derivatives thereof, as well as variants thereof as described herein below. Reference to clotting factor FVIII is meant to include all potential forms of such proteins and wherein each of the forms of FVIII has at least a portion or all of the native B domain sequence intact.

“Dosing interval,” as used herein, means an amount of time that elapses between multiple doses being administered to a patient. The dosing interval for administering a therapeutic plasma protein including clotting factor VIII may be at least about every one, two, three, four, five, six, seven, eight, nine, ten, eleven, twelve, thirteen, or fourteen days or longer. The dosing interval may change based on changing conditions/characteristics of a patient, changes to a minimally acceptable (e.g., target trough) concentration of the therapeutic plasma protein within a patient, and/or changes to a dosage.

FIG. 1 illustrates an example pharmacokinetic (PK) environment 100 in which a drug monitoring tool 150 operates, according to an example embodiment of the present disclosure. The environment 100 includes a remote server 120 that includes a model generator 125, QR generator 132, and PK server 130. The remote server 120 is communicatively coupled to a data store 115 that stores patent medical samples 110.

The model generator 125 is configured to generate one or more patient pharmacokinetic (PK) models based upon sampled patient data 110. The environment 100 also includes a pharmacokinetic (“PK”) server 130 that is configured to provide patients, healthcare providers, and/or sales representatives with a graphical pharmacokinetic drug dosing tool 150 based upon the one or more pharmacokinetic models. In the illustrated embodiment, the PK server 130 transmits the patient PK model to the drug monitoring tool 150 via a network 114 (e.g., an Internet). In other embodiments, the PK server 130 hosts the PK profile, which is accessible by the drug monitoring tool 150. In these other embodiments, the PK server 130 may include a single server, or alternatively, may be distributed within a cloud computing framework.

The example PK server 130 and/or the model generator 125 may be communicatively coupled to a database 115 configured to store the patient pharmacokinetic (PK) models. The database 115 may include any type of computer-readable medium, including RAM, ROM, flash memory, magnetic or optical disks, optical memory, or other storage medium. The example database 115 may also store information generated in response to users using the tool 150 including, for example, patient information, dosing regimes, etc. In some instances, the database 115 may be managed by a separate third-party storage provider.

In some instances, the PK server 130 and/or the model generator 125 may be provided by the same server (e.g., the remote server 120) and/or processor and/or operated by the same entity. In these instances, the functionality of the model generator 125 may operate in conjunction with the functionality of the PK server 130. For instance, the model generator 125 may periodically update pharmacokinetic models with therapeutic plasma protein dosing information and/or patient information received in the PK server 130 via the tool 150.

In some example embodiments, a pharmacokinetic (PK) model is used to approximate pharmacokinetic (PK) profiles of patients. For instance, current methods to determine a patient-specific pharmacokinetic profile for hemophilia A include performing multiple blood tests. These blood tests include performing an initial blood draw to determine a clotting factor VIII baseline in a patient. Then, after therapeutic plasma protein is administered, five or more blood draws are performed over a 48-hour post-infusion period. As can be appreciated, such a procedure is especially taxing on a patient, healthcare provider, and lab because of the numerous separate blood draws. Accordingly, the example model generator 125 is configured to generate relatively accurate pharmacokinetic models based upon a sample of patients with varying ages, body weights, genders, and activity levels. These models are then used to determine or approximate a pharmacokinetic profile of a patient without having to subject a patient to all of the blood draws and subsequent analysis.

In an embodiment, the PK models are determined using patient samples 110 selected from one or more sets of patient data. The patient samples 110 may be, for example, selected among patients who have already been subscribed a therapeutic dosing regimen using the above described blood draw procedure. The patient samples 110 may also include patients specifically selected to go through the blood draw procedure for the purpose of creating the models. The patient samples 110 may include patients from one hospital or medical system and/or patients associated from multiple hospitals, medical systems, geographic regions, etc.

The patient samples 110 include data for patients of varying ages, body weights (or body mass index (“BMI”), medical conditions, clinical laboratory data, genders, and/or activity levels. In the example described herein, sample patient ages vary between 2 and 100 years of age. In some embodiments, the data for the patients may be separated into children and adult age brackets such that a separate model is generated for each bracket. The patient data may additionally or alternatively be partitioned based on weight, gender, and/or activity level.

As mentioned, the example patient samples 110 include a determination of clotting factor VIII before therapeutic plasma protein is infused into the patients. Then, post infusion blood samples are collected from each patient after certain durations of time. It should be appreciated that in other examples, the blood samples may be collected at different times and/or the number of blood samples collected may be fewer or greater. For instance, fewer blood samples may be collected from children.

The example model generator 125 creates a PK patient model by performing a Bayesian analysis that uses previous knowledge of clotting factor VIII in the sampled patients over time after an infusion of the therapeutic plasma protein. In some instances, he model generator 125 is configured to analyze each patient's sampled dosing history in conjunction with pre-infusion clotting factor VIII levels, so that washout data is not needed to construct the PK models. In other embodiments, the model generator 125 may use patient washout data in conjunction with the post-infusion clotting factor VIII levels to create one or more pharmacokinetic models. Patient washout data corresponds to a baseline where the patient does not include the therapeutic plasma protein in their system.

The example model generator 125 creates the one or more PK models using, for example, the patient sample data. The model generator 125 may combine the individual patient samples 110 into one or more population profiles (e.g., age sets, weight sets, activity level sets, endogenous clotting factor VIII level, etc.), which is then used as a basis for the respective pharmacokinetic model. For instance, the model generator 125 may group the patient samples 110 for different ages, weights, and/or activity levels into different sets. The model generator 125 then performs covariate and statistical modeling on the grouped patient samples 110 of each set to create a population pharmacokinetic model for that set, as described in a white paper titled “Population pharmacokinetics of recombinant factor VIII—the relationships of pharmacokinetics to age and body weight”, by Björkman et al., the entirety of which is incorporated herein by reference. It should be appreciated however, that the model generator 125 may model the sampled data 110 using other Bayesian analysis techniques (e.g., a naïve Bayes classifier).

In the illustrated example, the covariate model used by the model generator 125 determines relationships between pharmacokinetic parameters (e.g., how quickly therapeutic plasma protein is metabolized, endogenous clotting factor VIII level, etc.) and patient characteristics (e.g., age, body weight, clinical laboratory data, gender, activity level, etc.). The model generator 125 uses a statistical model to determine variance in pharmacokinetic parameters among the sampled patients in addition to residual variance as a result of biological variability between patients, measurement errors, and errors within the fit of the sampled data 110 to the pharmacokinetic model.

The example model generator 125 is configured to perform the covariate and statistical modeling using non-linear mixed effects modeling with a first-order integral approximation method, as provided in SAS® software (NLMIXED procedure). In the illustrated example, the model generator 125 uses a two-compartment model. In other examples, the model generator 125 may use a single compartment model or three or more compartment models. In the illustrated two-compartment example, the first compartment includes pharmacokinetic parameters of clearance (“CL”) and volume of distribution (V1). CL refers to the amount of time for a patient to metabolize the therapeutic plasma protein in milliliters (“mL”) per hour per kilogram (“kg”). In other words, clearance is a measure of efficiency and rate at which a therapeutic plasma protein is removed or eliminated from a patient.

Responsive to creating one or more pharmacokinetic models, the model generator 125 provides the pharmacokinetic model(s) to the PK server 130. The transmission may be over a private network, such as a local area network, or over a public network, such as an Internet. The model generator 125 may also store the models to the database 115, which is also accessible by the PK server 130 via one or more interfaces. In other instances, the model generator 125 may be integrated with the PK server 130.

The example model generator 125 may refine the models for each patient. For instance, the PK server 130 may receive patient specific information including, weight, age, gender, endogenous clotting factor VIII level, and dosing level for previous treatments. The model generator 125 uses the previous treatment information (e.g., dosing amounts, intervals, etc.) to refine or adjust the model such that dosing recommendations and a pharmacokinetic profile are more aligned to the specific patient but still account for potential patient variance. The model generator 125 transmits the patient-specific model to the PK server 130.

Alternatively, the PK server 130 may be configured to create patient-specific models using the pharmacokinetic model provided by the model generator 125 to account for the patient-specific pharmacokinetic variance. In this manner, one or more base models are refined or adjusted by the PK server 130 responsive to receiving previous treatment information for a specific patient. The PK server 130 may be configured to store the patient-specific model to the database 115 for subsequent uses by the same healthcare provider or other healthcare providers.

Once a PK profile for a patient is generated, the PK server is configured to transmit the PK profile to the drug monitoring tool 150. In some embodiments, the PK server 130 can encrypt the data file prior to transmission. The encryption can be specific to a particular patient such that the drug monitoring tool 150 can only open and process a received PK profile if the tool 150 has a patient specific authentication key.

In other embodiments, the PK server 130 can provide the PK profile to the QR generator 132. The QR generator 132 can generate a quick response (QR) code that can be scanned by the drug monitoring tool 150 via scanner 160. The QR code can also be encrypted using known or yet to be known methods of encrypting QR codes. In some examples, the QR code encryption is specific to the patient for which the PK profile was generated. Accordingly, a drug monitoring tool 150 can only scan and process the QR code if the drug monitoring tool 150 includes appropriate security key(s) and decryption logic. Particularly, the QR code can be presented to the user of the drug monitoring tool 150. The user then scans the QR code using scanner 160. In some embodiments, the drug monitoring tool includes an activation toolkit 155. The activation toolkit 155 is configured to enable access to functionalities of the drug monitoring tool 150 in response to at least of: receiving the PK profile the patient and/or receiving a log of a first prophylactic infusion.

Once the drug monitoring tool 150 is activated, the tool 150, via processor(s) 165, generates an interactive user interface 175 for display on the tool 150. An example of the user interface 175 is further described herein in reference to, for example, FIG. 5. The user interface 175 is configured to display a graphical representation of a time-varying amount of the therapeutic plasma protein within the patient at any given time. The graphical representation delineating zones associated with the time varying amount of the therapeutic plasma protein. Each zone is associated with a particular concentration range of the time-varying amount of the therapeutic plasma protein within the patient.

The drug monitoring tool 150 can be communicatively coupled to an infusion pump 140 and a biological collector 135. The infusion pump 140 can be configured to automatically administer a particular clotting factor VIII drug based on a dosing regimen/treatment schedule. In some embodiments, the infusion pump 140 can be configured to administer a dose of the particular clotting factor VIII drug in response to results of a biological sample collected by the biological collector 135. For example, the collector 135 can collect a blood sample and determine a factor VIII level of the patients. In response to the amount, the infusion pump 140 can administer a dose of the particular clotting factor VIII drug.

Additionally, the environment 100 can include an ecosystem monitoring system 180 that is coupled to the network 105 and in communication with both the remote server 120 and drug monitoring tool. The system 180 can provide notification to a pharmacist to prepare the particular clotting factor VIII drug for purchase by a patient. For example, the system 180 can determine that the patient has a threshold amount of the drug left such that the patient will be in need of the drug in the near future. Similarly, the system 180 can contact a physician to ensure that physician has real-time information associated with the patient. Accordingly, the physician can take immediate actions to care of the patient if a need arises.

FIG. 2 is a flow diagram of a method 200 for generating a PK profile of a particular patient in accordance with an example embodiment of the present disclosure. The method 200, at 205, includes collecting patient information (e.g., patient sample 110, medical history, etc.). At 210, the method 200 includes generating a PK profile 210 for a patient. The PK profile can be generated as described in U.S. patent application Ser. No. 14/311,133 filed on Jun. 20, 2014 (now published as U.S. Pat. Pub. No. 2014/0379629 on Dec. 25, 2014). The entire teachings of which are incorporated herein by reference. The method 200, at 215, includes encoding the PK profile. In some examples, the PK profile can be encoded by the PK Server 130 using known or yet to be known electronic data encoding techniques. At 220, the method 200 includes transmitting the PK profile to a drug monitoring tool 150.

FIG. 3 is a flow diagram of a method 300 for converting a PK profile into a QR code in accordance with an example embodiment of the present disclosure. The method 300, at 310, includes extracting essential data points from a PK profile. For example, Table 1 below identifies information that is encoded into the QR code for an example patient:

TABLE 1 Field Name Position Description Example UTF8 Schema 0 Format identifier of message. 1 Version Clinic Patient 1 Patient ID from myPKFiT 153213465 ID Weight 2 Weight in kilograms 100.0 Alpha 3 Constants for FVIII estimate. 0.15305152251119972 Beta 4 Constants for FVIII estimate. 0.04031213652124507 K21 5 Constants for FVIII estimate. 0.12959298505994027 V1 6 Constants for FVIII estimate. 90.9144113054100 Duration 7 Schedule Type enumeration, Every 2 Days see below. Dosing 8 Custom schedule with 0 Interval Mon Monday infusion. 1 implies active. 0 implies inactive. Dosing 9 Custom schedule with 1 Interval Tues Tuesday infusion. 1 implies active. 0 implies inactive. Dosing 10 Custom schedule with 0 Interval Wed Wednesday infusion. 1 implies active. 0 implies inactive. Dosing 11 Custom schedule with 1 Interval Thursday infusion. 1 implies Thurs. active. 0 implies inactive. Dosing 12 Custom schedule with Friday 0 Interval Fri infusion. 1 implies active. 0 implies inactive. Dosing 13 Custom schedule with 1 Interval Sat Saturday infusion. 1 implies active. 0 implies inactive. Dosing 14 Custom schedule with 0 Interval Sun Sunday infusion. 1 implies active. 0 implies inactive. FVIII 15 Natural factor VIII baseline 5.0 Baseline for Factor Meter display. Target 16 Target trough for Factor 19.1 Trough Meter display. Time Above 17 Time above/green zone 79.9 threshold for Factor Meter Display. Time Below 18 Time below/red zone 10.1 threshold for Factor Meter Display. Report 19 Date myPKFiT assessment 2015-01-27T Timestamp for report identification. 04:41:32.0000000Z ISO-8601 format. UTC time reference. The method 300, at 320, then generates the QR code using information from Table 1 above. The method 300 can generate the QR code to have the patient information encrypted using AES-256 encryption with cipher block chaining (CBC) and public-key cryptography standards (PKCS) padding.

FIG. 4 illustrates an interactive user interface 400 of a drug monitoring tool (e.g., the tool 150 of FIG. 1) in accordance with an example embodiment of the present disclosure. The interactive user interface is configured to display a graphical representation 405 of a time-varying amount of the therapeutic plasma protein within the patient at any given time. In this example, the representation is that of a battery. Those skilled in the art will understand that any representation could be used to convey the time-varying nature of a drug level. The graphical representation 405 delineating zones 415 a-c associated with the time varying amount of the therapeutic plasma protein. For example, a safe zone 415 a indicates that levels of the clotting factor VIII are considered safe for many anticipated activity levels. A warning zone 415 b provides an indication to a patient that they should carefully select an activity level in order to prevent a bleed event. The danger zone 415 c indicates that the patient should administer another dose of the particular clotting factor VIII drug in the near future. The danger zone 415 c also provides an indication to the patient that activity levels should be kept to a minimum.

The interface 400 also includes a representation of a current drug level (e.g., Factor level) of a drug (e.g., a specific clotting factor VIII drug). The interface 400 further includes a graphical control element 410 configured to receive patient input corresponding to a request for the time-varying amount of the therapeutic plasma protein within the patient at a particular time. In response to a patient sliding the graphical control element 410, the interactive user interface 400 is configured to display the time varying amount of the therapeutic plasma protein within the patient at the particular time corresponding to a position of the graphical control element 410.

FIG. 5 is a detailed block diagram of an example computing device 3000. The computing device 3000 can be any communication device such as a desktop computer, laptop computer, server system, cloud-based computing system, wireless transmit/receive unit (WTRU) (e.g., smartphone, tablet computer, mobile phone, personal digital assistant (PDA), etc.). Accordingly, the computing device 3000 can be, for example, the remote server 120, drug monitoring tool 150, and/or the ecosystem monitoring system 180.

In this example, the device 3000 includes a main unit 3102. The main unit 3102 preferably includes one or more processors 3104 communicatively coupled by an address/data bus 3106 to one or more memory devices 3108, other computer circuitry 3110, and one or more interface circuits 3112. The processor 3104 may be any suitable processor, such as a microprocessor from the INTEL PENTIUM® or CORE™ family of microprocessors. The memory 3108 preferably includes volatile memory and non-volatile memory. Preferably, the memory 3108 stores a software program that interacts with the other devices in the environment 100, as described above. This program may be executed by the processor 3104 in any suitable manner. In an example embodiment, memory 3108 may be part of a “cloud” such that cloud computing may be utilized by the device 3000. The memory 3108 may also store digital data indicative of documents, files, programs, webpages, patient samples, pharmacokinetic models, patient pharmacokinetic profiles, etc. retrieved from (or loaded via) the device 3000.

The example memory devices 3108 store software instructions 3123, patient samples/pharmacokinetic models 3124, application interfaces 3126, user interface features, permissions, protocols, identification codes, content information, registration information, event information, and/or configurations. The memory devices 3108 also may store network or system interface features, permissions, protocols, configuration, and/or preference information 3128 for use by the device 3000. It will be appreciated that many other data fields and records may be stored in the memory device 3108 to facilitate implementation of the methods and apparatus disclosed herein. In addition, it will be appreciated that any type of suitable data structure (e.g., a flat file data structure, a relational database, a tree data structure, etc.) may be used to facilitate implementation of the methods and apparatus disclosed herein.

The interface circuit 3112 may be implemented using any suitable interface standard, such as an Ethernet interface and/or a Universal Serial Bus (USB) interface. One or more input devices 3114 may be connected to the interface circuit 3112 for entering data and commands into the main unit 3102. For example, the input device 3114 may be a keyboard, mouse, touch screen, track pad, track ball, isopoint, image sensor, character recognition, barcode scanner, microphone, and/or a speech or voice recognition system.

One or more displays, printers, speakers, and/or other output devices 3116 may also be connected to the main unit 3102 via the interface circuit 3112. The display may be a cathode ray tube (CRTs), a liquid crystal display (LCD), or any other type of display. The display generates visual displays generated during operation of the device 3000. For example, the display may provide a user interface and may display one or more webpages received from the device 3000. A user interface may include prompts for human input from a user of the device 3000 including links, buttons, tabs, checkboxes, thumbnails, text fields, drop down boxes, etc., and may provide various outputs in response to the user inputs, such as text, still images, videos, audio, and animations.

One or more storage devices 3118 may also be connected to the main unit 3102 via the interface circuit 3112. For example, a hard drive, CD drive, DVD drive, and/or other storage devices may be connected to the main unit 3102. The storage devices 3118 may store any type of data, such as identifiers, identification codes, registration information, patient samples, patient information, pharmacokinetic models, patient pharmacokinetic profiles, treatment regimes, statistical data, security data, etc., which may be used by the device 3000.

The computing device 3000 may also exchange data with other network devices 3120 via a connection to a network 3121 (e.g., the Internet) or a wireless transceiver 3122 connected to the network 3121. Network devices 3120 may include one or more servers, which may be used to store certain types of data, and particularly large volumes of data which may be stored in one or more data repository. A server may process or manage any kind of data including databases, programs, files, libraries, identifiers, identification codes, registration information, content information, patient samples, patient information, pharmacokinetic models, patient pharmacokinetic profiles, treatment regimes, statistical data, security data, etc. A server may store and operate various applications relating to receiving, transmitting, processing, and storing the large volumes of data. It should be appreciated that various configurations of one or more servers may be used to support, maintain, or implement the device 3000 of the environment 100. For example, servers may be operated by various different entities, including operators of the PK server 108, hospital systems, patients, drug manufacturers, service providers, etc. Also, certain data may be stored in the device 3000 which is also stored on a server, either temporarily or permanently, for example in memory 3108 or storage device 3118. The network connection may be any type of network connection, such as an Ethernet connection, digital subscriber line (DSL), telephone line, coaxial cable, wireless connection, etc.

Access to the device 3000 can be controlled by appropriate security software or security measures. An individual third-party client or consumer's access can be defined by the device 3000 and limited to certain data and/or actions. Accordingly, users of the environment 100 may be required to register with the computing device 3000.

While this disclosure has been particularly shown and described with references to example embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the present disclosure encompassed by the appended claims. 

What is claimed is:
 1. A drug monitoring tool, the tool comprising: a data receiver configured to receive, from a secured server, a patient pharmacokinetic (PK) profile of a patient, wherein the secured server comprises: (I) a Bayesian model of pharmacokinetic (PK) profiles of sampled patients, the Bayesian model including (i) a therapeutic plasma protein clearance and (ii) a volume of distribution relationship for a therapeutic plasma protein based upon at least one of patient age or body weight, and (II) a PK server configured to determine the patient PK profile based upon the Bayesian model, and at least one of a bodyweight, von Willebrand factor level, and an age of the patient; and an interactive user interface configured to: display to the patient a graphical representation predictive of a time-varying therapeutic plasma protein level of the patient, the time-varying therapeutic plasma protein level determined by the drug monitoring tool based on the timing and amount of an administered dose of a clotting factor VIII to the patient and the patient PK profile; and delineate a plurality of zones within the graphical representation associated with the time-varying therapeutic plasma protein level, the plurality of zones comprising at least: a safe zone indicating to the patient that the time-varying therapeutic plasma protein level is within a first concentration range considered safe for physical activity; and a danger zone indicating to the patient that the time-varying therapeutic plasma protein level is within a second concentration range and physical activity should be limited.
 2. The drug monitoring tool of claim 1, wherein: the data receiver is a camera configured to scan a quick response (QR) code storing patient information that includes at least PK profile information; and the drug monitoring tool further comprising a QR code processor configured to extract and process the patient PK profile.
 3. The drug monitoring tool of claim 2, further comprising a QR code generator configured to generate the QR code having patient information encrypted using AES-256 encryption with cipher block chaining (CBC) and public-key cryptography standards (PKCS) padding.
 4. The drug monitoring tool of claim 3, wherein the QR code generator is located at the secured server remote from the drug monitoring tool.
 5. The drug monitoring tool of claim 1, further comprising an activation toolkit that allows the drug monitoring tool to provide the graphical representation predictive of the time-varying therapeutic plasma protein level only after receiving the patient PK profile and a log of a first prophylactic infusion.
 6. The drug monitoring tool of claim 1, wherein the interactive user interface includes a graphical control element configured to receive patient input corresponding to a request for the time-varying therapeutic plasma protein level within the patient at a particular time selected by the patient; and wherein the interactive user interface is configured to display the graphical representation of the time-varying therapeutic plasma protein level within the patient at the particular time.
 7. The drug monitoring tool of claim 6, wherein the graphical control element is slidable between the plurality of zones.
 8. The drug monitoring tool of claim 1, wherein the graphical representation provides an estimated amount of time until the time-varying therapeutic plasma protein level reaches the danger zone.
 9. A drug monitoring system, the system comprising: a remote server system comprising: a Bayesian model of pharmacokinetic (PK) profiles of sampled patients, the Bayesian model including (i) a therapeutic plasma protein clearance and (ii) a volume of distribution relationship for a therapeutic plasma protein based upon at least one of patient age or body weight, a PK server that determines a patient PK profile based upon the Bayesian model and at least one of a bodyweight, von Willebrand factor level, and an age of a patient, and a quick response (QR) code generator that generates a QR code storing the patient PK profile; and a drug monitoring tool comprising: a camera that reads the QR code, a code processor that extracts the patient PK profile from the QR code, and an interactive user interface that displays a graphical representation of a time-varying therapeutic plasma protein level of the patient determined by the drug monitoring system based on the timing and amount of an administered dose of a clotting factor VIII to the patient and the patient PK profile, the graphical representation delineating a plurality of zones within the graphical representation associated with the time-varying therapeutic plasma protein level, the plurality of zones comprising at least: a safe zone indicating to the patient that the time-varying therapeutic plasma protein level is within a first concentration range considered safe for physical activity; and a danger zone indicating to the patient that the time-varying therapeutic plasma protein level is within a second concentration range and physical activity should be limited.
 10. The system of claim 9, wherein the quick response (QR) code generator generates the QR code using a plurality of fields each independently selected from the group consisting: schema version, clinic patient ID, weight, alpha, beta, K21, V1, duration, dosing interval, FVIII baseline, target, trough, time above, time below, and timestamp.
 11. The system of claim 9, wherein the quick response (QR) code generator generates the QR code using a plurality of fields, each field encoded using UTF8.
 12. The system of claim 9, wherein the graphical representation provides an estimated amount of time until the time-varying therapeutic plasma protein level reaches the danger zone.
 13. A method of using a patient pharmacokinetic (PK) profile to predict drug levels, the method comprising: receiving, at a user device, a patient PK profile for a clotting factor from a server system that determines the patient PK profile based on a Bayesian model of sampled patients and at least one of a bodyweight, a von Willebrand factor level, and an age of a patient; determining, by the user device, time-varying levels of the clotting factor predicted using the patient PK profile to result in the patient from the timing and amount of an administered dose of the clotting factor; and displaying, via an interactive user interface of the user device, the time-varying levels of the clotting factor predicted in the patient within a plurality of zones, the time-varying levels of the clotting factor being positioned within either: a safe zone indicating to the patient that the time-varying levels of the clotting factor is within a first concentration considered safe for physical activity; or a danger zone indicating to the patient that the time-varying levels of the clotting factor is within a second concentration and physical activity should be limited.
 14. The method of claim 13, further comprising: providing a graphical control element by which a user can inquire about the time-varying levels of the clotting factor at a particular time selected by the user; and displaying a first estimated level of the clotting factor predicted using the patient PK profile to be in the patient at the particular time.
 15. The method of claim 14, wherein the graphical control element is slidable between the plurality of zones.
 16. The method of claim 13, wherein the Bayesian model comprises (i) a clotting factor clearance and (ii) a volume of distribution relationship for the clotting factor based on age or bodyweight of the sampled patients.
 17. The method of claim 13, wherein: receiving the patient PK profile includes using the user device for: scanning a quick response (QR) code storing patient information that includes at least PK profile information; and extracting and processing the patient information stored within the QR code.
 18. The method of claim 17, wherein the server system generates the QR code having patient information encrypted using AES-256 encryption with cipher block chaining (CBC) and public-key cryptography standards (PKCS) padding.
 19. The method of claim 17, wherein the QR code includes at least one of or any combination of: patient identifying information, patient physiological data, patient dosing information, and/or PK profile information of the patient, wherein the patient dosing information includes a prophylactic dosing regimen for a particular clotting factor VIII drug.
 20. The method of claim 13, further comprising performing, for the patient, the determining step and the displaying step in response to receiving the patient PK profile and a log of a first prophylactic infusion. 